From b4f3219fb2f330fe80d1aa16b6ef554fc902579a Mon Sep 17 00:00:00 2001 From: "kaf24@scramble.cl.cam.ac.uk" Date: Fri, 16 Jan 2004 09:42:47 +0000 Subject: [PATCH] bitkeeper revision 1.678 (4007b217AoX5mBnjK4x2dP2OVMNLew) entry.S: Another small build fix for earlier gcc's. --- xen/arch/i386/entry.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xen/arch/i386/entry.S b/xen/arch/i386/entry.S index 7ff44fd3e5..08824dd920 100644 --- a/xen/arch/i386/entry.S +++ b/xen/arch/i386/entry.S @@ -642,9 +642,9 @@ ENTRY(nmi) movl %eax,%ebx # Okay, its almost a normal NMI tick. We can only process it if: - # 1. We are the outermost Xen activation (in which case we have + # A. We are the outermost Xen activation (in which case we have # the selectors safely saved on our stack) - # 2. DS-GS all contain sane Xen values. + # B. DS-GS all contain sane Xen values. # In all other cases we bail without touching DS-GS, as we have # interrupted an enclosing Xen activation in tricky prologue or # epilogue code. -- 2.30.2